Faults and Warning Messages
A warning is generally a notification to the user which is not critical and does not require the machine to immediately shut off. A fault is generally a notification of a critical system failure which will stop machine operation. Depending on the severity of the fault will depend on which system-stop mechanism is used.
Faults and warnings follow the same pattern and are identified by a four digit code:
G G X X
where GG is a two digit group code, and XX is a two digit ID. All faults and warnings are grouped together to easily identify what part of the system is having trouble.
| Group | Group # |
|---|---|
| 10 | System |
| 11 | File |
| 15 | Hardware |
| 20 | Power |
| 25 | Temperature |
| 30 | Software |
| 4# | Feedback (# indicates feedback number) |
| 50 | Motor |
| 55 | Wake and Shake |
| 60 | Motion |
| 70 | Fieldbus A Fieldbus is an industrial network system for real-time distributed control (e.g. CAN or Profibus). It is a way of connecting instruments in a plant design
|
| 90 | Safety |
Retrieving Fault and Warning Information
Users can retrieve faults on a per-axis basis with: AXIS#.FAULTS, where # is the axis number. Similarly, users can retrieve per-axis warnings with AXIS#.WARNINGS.
DRV.FAULTS returns faults across all axes, with the format X-#### where X is the axis number and #### is the four digit fault code. DRV.WARNING provides warnings across all axes with a similar format.
Feedback faults are reported with axis faults if the feedback is configured as a feedback source for the axis (e.g. AXIS#.IL.FBSOURCE, AXIS#.VL.FBSOURCE, AXIS#.PL.FBSOURCE). If a feedback is not a feedback source for an axis, its faults can be read with FB#.FAULTS where # is the feedback number.
Clearing Faults and Warnings
Once fault conditions have been corrected, users can clear faults on an axis using AXIS#.CLRFAULTS. To clear faults on all axes with a single command, DRV.CLRFAULTS can be used.
The action table can also be used to clear faults. Action task 12: Clear Faults can be configured to trigger on edge conditions of the action sources. The action task ID selects the axis on which to clear faults.
The hardware enable input can also be used to clear faults. If AXIS#.HWEN.MODE is 0, faults for the axis are cleared on the rising edgeA rising edge is the transition of a digital signal from low to high. It is also called positive edge of the hardware enable signal.
Fault History
Faults are logged to flash memory for convenience and debugging. To retrieve the last 50 faults with timestamps, use the keyword DRV.FAULTHIST.
To retrieve a more extensive history of faults, use DRV.FAULTHIST/all.
Fault Table
A list of all possible faults and warnings can be found by using the keywords DRV.FAULTLIST and DRV.WARNINGLIST.
| Error | Description | Cause | Remedy |
|---|---|---|---|
| F1000 | Firmware and FPGA"Field-Programmable Gate Array"
FPGA is a semiconductor device that can be configured by the customer or designer after manufacturing; hence the name "field-programmable" versions are not compatible. |
The FPGA version does not match the firmware FPGA version constants. | Load the FPGA version that is compatible with the firmware. |
| F1001 | Power Board type mismatch detected | Power Board image does not match what operational firmware expected | Contact customer support to update the drive. |
| F1002 | Power Board Communication fault. | Communications with the Power Board Failed | AXIS#.CLRFAULTS . If issue persists, contact technical support. |
| F1003 | Power Board FPGA not configured. | Communications with the Power Board Failed | AXIS#.CLRFAULTS . If issue persists, contact technical support. |
| F1004 | Failed to initialize the system | Failure in primary module during software start-up | Contact Customer support |
| F1005 | Unrecognized FPGA Fault |
Failure within the FPGA Module. FPGA reported unrecognized fault. |
Issue AXIS#.CLRFAULTS , if problem persists contact Customer Support |
| F1006 | FPGA cyclic read fault. | Detected a timing issue between the firmware and FPGA. | Power cycle the drive. If the fault occurs again, contact Customer Support. |
| F1007 | A Factory MechaWare model failed to load. | Failed to read the control loop model from flash. | Power cycle the drive. If the fault occurs again, contact Customer Support. |
| F1100 | NV Memory Data (might occur when downloading firmware). | Non-volatileinformation is stored in a specific memory to remain accessible even when the application has been powered off memory data is corrupted or invalid. When this fault occurs after a firmware download, it is not an indication of a problem (clear the fault and perform a “save” to the drive). |
Reset the drive to default memory values using Parameter Load in WorkBench. |
| F1101 | Flash Directory Error | File System in unexpected state | Download latest firmware, if problems persist, contact Customer Support |
| F1102 | Identity Read Failed | EDS information on the drive is not in expected format | Contact Customer Support |
| F1103 | Invalid MAC Address | The MAC Address stored in the EDS on the drive is invalid | Contact Customer Support |
| F1104 | Power Board factory settings file read failed | Power Board settings unable to be retrieved | Contact Customer Support |
| F1105 | Power Board updateable settings file read failed | Power Board settings unable to be loaded | Contact Customer Support |
| F1106 | Failure reading Control Board FPGA EDS file | Control Board configuration settings unable to be loaded | Contact Customer Support |
| F1107 | Power Board Resident FPGA not valid | Power Board Resident FPGA not valid | Update to latest firmware, if problem persists, contact Customer Support |
| F1108 | Power Board Operational FPGA not valid | Power Board Operational FPGA not valid | Download latest firmware, if problem persists, contact Customer Support. |
| F1109 | Failure reading Power Board FPGA EDS | Failure reading Power Board FPGA EDS | Contact Customer Support |
| F2000 | Vbus read is out of thresholds. | Hardware problem in bus measurement. | Troubleshoot and repair hardware problem. |
| F2001 | Drive Foldback. | Maximum drive power has been exceeded. The power has been limited to protect the drive. | Motion requires too much power. Change profile to reduce load . |
| F2002 | Output over current. | Current exceeds drive peak. | Check for short or feedback faults. |
| F2003 | Current sensorA sensor is a type of transducer that converts one type of energy into another for various purposes including measurement or information transfer short circuit. |
1. Current sensor short circuit. 2. Motor cable plugged in upside down | 1. Restart drive. If issue persists, contact technical support. 2. Plug in cable right-side up. |
| F2004 | Iu current offset limit exceeded. | Hardware failure detected. | Restart drive. If issue persists, contact technical support. |
| F2005 | Iv current offset limit exceeded. | Hardware failure detected. | Restart drive. If issue persists, contact technical support. |
| F2006 | Bus over voltage. | Bus voltage too high. Usually, this problem is load related. | Reduce load or change motion profile. Check system regen capacity; add capacity if needed. Check mains voltage. |
| F2007 | Bus under voltage. Warning issued prior to fault. | Bus voltage below threshold value. | Check mains voltage. |
| F2008 | Bus capacitor overloaded. | Single phase AC input on a drive only rated for three-phase input or excessive single-phase power load. | Check mains voltage. |
| F2009 | Regen near capacity, could not prevent over voltage. | An F501 Bus Over Voltage has occured while the Regen Resistor was at or above 75% of its dissipation capacity. | Increase the size of regen resistor to be able to dissipate more power. |
| F2010 | Regen over power. | Too much power stored in regen resistor. | Either get larger regen resistor or use DC bus sharing to dissipate power. |
| F2011 | Voltage exceeds motors rating. | Drive bus voltage exceeds the motor’s defined voltage rating. | Make sure that the motor fits the driving rating. |
| F2012 | Power Stage Fault | Power Stage Fault | Clear Faults, if problem persists, contact Customer Support |
| F2013 | Regen short circuit. | Regen resistor short circuit. | Regen IGBT short circuit. Contact technical support. |
| F2014 | AC input phase loss. | Phase loss detected when axis enabled on drive with three-phase AC input.. | Check mains power voltage. If AC input is single phase, set VBUS.THREEPHASE to 0. |
| F2015 | Bus over voltage FPGA. | Bus over voltage hard fault. | Check mains voltage and check system brake capacity. |
| F2016 | Gate Supply under voltage |
Gate Supply under voltage. |
Check wiring, if problems persist, contact Customer Support |
| F2018 | Broken Wire Connection to Motor. | At least one of the motor phases are not connected to the drive. For this fault detection to properly work, motor parameters must be set correctly. | Fix wire connections to the motor. If motor parameters are not set automatically, check motor parameters. |
| F2500 | Control over temperature sensor 1. | High temperature limit reached. | Check cabinet ventilation system. |
| F2501 | Power over temperature sensor 1. | High temperature limit reached. | Check cabinet ventilation system. |
| F2502 | Control under temperature sensor 1. | Low temperature limit reached. | Check cabinet ventilation system. |
| F2503 | Power under temperature sensor 1. | Low temperature limit reached. | Check cabinet ventilation system. |
| F3000 | Issue command timed out. | Processing a command took longer than the command timeout (10-60 sec depending on the command). | Try reducing the CPU load of the drive by deactivating unused features or changing the fieldbus cycle time. |
| F3001 | Negative limit switch triggered. | Either a digital input is configured as negative limit switch (DINx.MODE 19) and its state is “off” OR a negative software position limit is configured (AXIS#.SWLS.EN) and the actual position AXIS#.PL.FB is less than the configured limit (see also AXIS#.SWLS.LIMIT# / ). | Move the load away from the limits. |
| F3002 | Assert Check Failed | Internal Firmware Error | Contact Customer Support |
| F3003 | External Fault. | This fault is user generated and is caused by user settings. | Users can configure a digital input to trigger this fault (DINx.MODE = 10). The fault occurs according to this input setting. Clear the input to clear the fault. |
| F3004 | Operation in Position Mode with Halls Only feedback not allowed. | Operation in Position Mode with Halls Only feedback not allowed. | Set your drive’s mode of operation to velocity or torqueTorque is the tendency of a force to rotate an object about an axis. Just as a force is a push or a pull, a torque can be thought of as a twist when using a Halls Only feedback. |
| F3005 | Thread watchdog | Unresponsive firmware thread | Clear Faults, if problem persists, contact Customer Support. |
| F3100 | MechaWare Model failed to connect Analog Input, fix model. | A MechaWare model contains an Analog Input block with an invalid Analog Input number. | Fix Analog Input blocks to have valid Analog Input numbers |
| F3101 | MechaWare Model failed to connect Analog Output, fix model. | A MechaWare model contains an Analog Output block with an invalid Analog Output number. | Fix Analog Output blocks to have valid Analog Output numbers |
| F3102 | MechaWare Models are missing Motor TorqueTorque is the tendency of a force to rotate an object about an axis. Just as a force is a push or a pull, a torque can be thought of as a twist block, fix model. |
Across all of the active MechaWare models, there is no Torque Output for all axes. |
1) Verify models are turned on 2) If using User Models, check that models contain a Motor Torque block, and the axis number is correct |
| F4000 | Feedback Parity Fault | Feedback Parity Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4001 | Feedback Overrun Fault | Feedback Overrun Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4002 | Feedback Framing Fault | Feedback Framing Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4003 | Feedback CRC"Cyclic redundancy check"
A CRC is a type of function that takes as input a data stream of any length and produces as output a value of a certain fixed size. The term CRC is often used to denote either the function or the function's output. A CRC can be used as a checksum to detect accidental alteration of data during transmission or storage Fault |
Feedback CRC Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4004 | Feedback Communication Timeout Fault | Feedback Communication Timeout Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4005 | Feedback Initialization Sequence Fault | Feedback Initialization Sequence Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4006 | Feedback Temperature Fault | Feedback Temperature Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4007 | Feedback battery Fault | Feedback battery Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4008 | Feedback SensorA sensor is a type of transducer that converts one type of energy into another for various purposes including measurement or information transfer Fault |
Feedback Sensor Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4009 | Feedback DeviceA process whereby some proportion of the output signal of a system is passed (fed back) to the input.
In automation, a device coupled to each motor to provide indication of the motor's shaft angle, for use in commutating the motor and controlling its speed and position-Unique Fault 0 |
Feedback Device-Unique Fault 0 | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4010 | Feedback Device-Unique Fault 1 | Feedback Device-Unique Fault 1 | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4011 | Feedback Analog Signal Fault | Feedback Analog Signal Fault | Check Feedback Settings, if problem persists, Contact Customer Support |
| F4012 | Feedback Broken Wire | Feedback Broken Wire | Check Feedback Wiring |
| F4013 | Feedback Power Supply Fault | Feedback Power Supply Fault | Check Feedback Wiring |
| F4014 | Feedback, Illegal Hall State (111, or 000) | Feedback, Illegal Hall State (111, or 000) | Check Hall Wiring |
| F4015 | Failed to set feedback type | Failed to set feedback type | Check Feedback Settings and wiring |
| F4016 | Failed to read motor parameters from feedback deviceA process whereby some proportion of the output signal of a system is passed (fed back) to the input.
In automation, a device coupled to each motor to provide indication of the motor's shaft angle, for use in commutating the motor and controlling its speed and position. |
Motor either does not have motor feedback memory, or the motor feedback memory is not programmed properly so the parameters cannot be read. | Try to read parameters again by clicking the Disable and Clear Faults button, or by issuing the AXIS#.CLRFAULTS command. If this attempt is not successful, then set AXIS#.MOTOR.AUTOSET to 0 (off) and program the parameters using the setup wizard or manually set up the parameters. If the motor has motor memory (Biss Analog, Endat, and SFD motors have motor memory), return the motor to have the memory programmed. |
| F4017 | SFA communication fault | Communication error between the SFA and the drive. | Check cabling between the SFA and the Drive. |
| F4018 | SFA over current | Feedback power supply over current. | Check for short-circuit in the cable between the SFA and the drive. |
| F4019 | SFA under voltage | High wire resistance or short on cable between SFA and Drive. | Check for loose wiring between the SFA and the Drive. |
| F4020 | Feedback: Safety fault | Feedback safety system has faulted | Check for damaged encoder. Replace if problem persists. |
| F4021 | Feedback: Watchdog fault | Feedback subsystem stopped responding | Internal system fault. Report failure to Kollmorgen |
| F4022 | Unrecognized feedback fault | FPGA reported unrecognized fault | Issue AXIS#.CLRFAULTS, if problem persists contact Customer Support |
| F5000 | Motor overheated. | Motor overheated. | Check ambient temperature. Check motor mounting heat sink capability |
| F5001 | Brake 1 Current out of range | Brake 1 Current out of range | Check Brake Wiring |
| F5002 | Brake 2 Current out of range | Brake 2 Current out of range | Check Brake Wiring |
| F5003 | Brake applied during Enable-State. | Motor brake closed unexpectedly. | Check cabling and general functionality. |
| F5004 | Brake released when it should be applied. | Brake disengaged unexpectedly. | Check cabling and general functionality. |
| F5005 | Drive motor parameters setup incomplete. | Before a motor can be enabled, you must configure a minimum set of parameters. These parameters have not been configured. | Issue the command AXIS#.SETUPREQLIST to display the list of the parameters that you must configure. Configure these parameters either manually or automatically. You can manually configure these parameters in three ways: (1) set each parameter individually; (2) use the setup wizard to select the motor; or (3) select the motor type from the motor data base in the Motor window (AXIS#.MOTOR.AUTOSET must be set to 0 (off)). If you use the Motor window, you must first select the feedback type. If the motor has Biss Analog, Endat, or SFD feedback (feedback with memory), then these parameters are set automatically when AXIS#.MOTOR.AUTOSET is set to 1 (on). |
| F5500 | Wake and Shake - Insufficient movement | There was less movement than defined by AXIS#.WS.DISTMIN . | Increase AXIS#.WS.IMAX and/or AXIS#.WS.T . Or try using AXIS#.WS.MODE 1 or 2. |
| F5501 | Wake and Shake - Excess movement | AXIS#.WS.DISTMAX has been exceeded in AXIS#.WS.MODE 0. Or more than 360 degrees was traveled in AXIS#.WS.MODE 2. | Increase AXIS#.WS.DISTMAX value or reduce AXIS#.WS.IMAX or AXIS#.WS.T . Wake and Shake is not suported for vertical/overhung loads. |
| F5502 | Wake and Shake - Fine-Coarse delta too large. | The angle difference between the coarse and fine calculation was larger than 72 deg. | Modify AXIS#.WS.IMAX or AXIS#.WS.T and try again. |
| F5503 | Wake and Shake - Over speed | AXIS#.WS.VTHRESH was exceeded. | Increase AXIS#.WS.VTHRESH value or reduce AXIS#.WS.IMAX or AXIS#.WS.T . |
| F5504 | Wake and Shake - Loop angle delta too large. | The angle between complete loops was larger than 72 deg. | Modify AXIS#.WS.IMAX or AXIS#.WS.T and try again. |
| F5505 | Wake and Shake - Commutation not initialized. | The motor requires the commutation initialization (there are no encoder commutation tracks, Hall sensors, etc.) and no successful Wake and Shake sequence has been performed | Clear any faults, activate the Wake and Shake procedure (AXIS#.WS.ARM ) and enable the drive. |
| F5506 | Wake and Shake - Motor U phase missing. | No current was detected in the motor's U phase during Wake and Shake initialization (Mode 0 only). | Check the motor connections and AXIS#.WS.IMAX (very low current may produce this error). |
| F5507 | Wake and Shake - Motor V phase missing. | No current was detected in the motor's V phase during Wake and Shake initialization (Mode 0 only). | Check the motor connections and AXIS#.WS.IMAX (very low current may produce this error). |
| F5508 | Wake and Shake - Motor W phase missing. | No current was detected in the motor's W phase during Wake and Shake initialization (Mode 0 only). | Check the motor connections and AXIS#.WS.IMAX (very low current may produce this error). |
| F5509 | Wake and Shake - Validating Positive Movement Failed. | After applying a positive current, motor moved in the wrong direction. | Check motor phase wiring and motor encoder wiring is correct. |
| F5510 | Wake and Shake - Validating Negative Movement Failed. | After applying a negative current, motor moved in the wrong direction. | Check motor phase wiring and motor encoder wiring is correct. |
| F5511 | Wake and Shake - Validating Comm. angle timed out. | During one of the W&S validation stages, the drive stopped responding to commands. | Contact customer support. |
| F5512 | Wake and Shake - Validating Comm. angle moved too far - Bad Comm Angle. | After applying a current, the motor moved too far (>15 electrical degrees). | This indicates a poor motor phase angle was found by Wake and Shake. Revise Wake and Shake parameters, and re-run Wake and Shake. |
| F5513 | Wake and Shake - Validating Comm. angle required more than AXIS#.MOTOR.ICONT | A current larger than AXIS#.MOTOR.ICONT was used to excite the motor. | This indicates one of the following: •Phase angle is incorrect due to a bad wake and shake. •Motor has very high friction requiring high current to break free. •Motor power cable is disconnected or improperly wired. |
| F6000 | Over speed | Motor exceeded AXIS#.VL.THRESH | Increase AXIS#.VL.THRESH or lower velocity command |
| F6001 | Following error magnitude fault. | Motor did not follow command values. Motor exceeded maximum allowed position following error (user). | Check feedback commutation setup and tuning parameters. |
| F6002 | Invalid commutation detected - motor accelerating in the wrong direction. Motor phase may be incorrect. | The velocity of the motor exceeded AXIS#.WS.CHECKV and the sign of the current was not equal to the sign of motor acceleration or the sign of motor velocity for a period of time larger than AXIS#.WS.CHECKT. | 1. Check motor phase wiring 2. Re-configure wake and shake (if Mode 0 or 1 is used) 3. Re-run wake and shake to determine correct commutation angle |
| F6003 | Instability during autotune. | Drive current (AXIS#.IL.CMD ) or velocity feedback (AXIS#.VL.FB ) exceeds allowable limit (AXIS#.BODE.IFLIMIT or AXIS#.BODE.VFLIMIT). This fault only occurs in AXIS#.BODE.MODE 5. This fault often occurs when complex mechanics, belts, and compliant loads are present. | Change AXIS#.BODE.MODE if appropriate. If AXIS#.BODE.MODE 5 is appropriate and the fault occurs at the end of an Autotuning, then the motor is not robustly stable. You can manually adjust Autotuner settings. Manual tuning may be required to make the motor stable. |
| F6004 | Target position was overshot due to invalid motion task activation. | The drive cannot decelerate from its current speed to reach the end point of the second motion task without moving past it. Increase the deceleration rate in the move or trigger the move earlier. | Change Motion task profile and clear fault with AXIS#.CLRFAULTS . Or change the value of FAULT139.ACTION = 1 to ignore this condition. |
| F6005 | Emergency timeout occurred. | Motor did not stop in the timeout defined in AXIS#.DISTO | Change timeout value, change stop parameters, improve tuning. |
| F6006 | Current home mode requires AXIS#.HOME.IPEAK to be set. | Some homing modes require AXIS#.HOME.IPEAK to be a non-zero value. | Set AXIS#.HOME.IPEAK to a non-zero value or use a different homing mode (AXIS#.HOME.MODE). |
| F6028 | Gear feedback source is invalid. | The feedback selected as the gearing source is either uninitialized or assigned to the same feedback being used as the commutation, velocity, or position feedback source. | Verify AXIS#.GEAR.FBSOURCE is not 0 and does not match the feedback being used for AXIS#.IL/VL/PL.FBSOURCE |
| F7000 | Fieldbus Communication lost. | All fieldbus communication was lost. | Check fieldbus connections, settings, and control unit. |
| F7001 | Fieldbus Sync frames lost. | The fieldbus lost synchronization. | Check fieldbus connection, or the settings of your EtherCATEtherCAT is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT was to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs or CANopen master. |
| F7002 | Fieldbus Heartbeat lost. | Heartbeat lost. | Check CANopen cabling. Reduce bus load or increase the heartbeat update time. |
| F7003 | Fieldbus PLL failed to lock | Fieldbus PLL failed to lock | Check Fieldbus wiring and settings |
| F7004 | Fieldbus PLL lost lock | Fieldbus PLL lost lock | Check fieldbus wiring and settings |
| F7005 | Fieldbus cyclic setpoints missing | Fieldbus communication interrupted for some reason | Check fieldbus wiring and settings |
| F9000 | Safe torque off. | Safe torque off function has been triggered. | Reapply supply voltage to STO if safe to do so. |
| F9002 | SMM Communication Failed | Safe Motion Module not communicating as expected | Contact Customer Support |
| F9003 | Incorrect safety card detected | Physical SMM module does not match the expected module | Contact Customer Support |
| F9004 | Safe torque off pulse and standard lines don't match | The two STO inputs did not change state within 100ms of each other. | With Pass through: Clear faults With SMM: clear safety IO fault with safe input configured with SAFE.IOERRORACKSOURCE or via FSoE. |
| F9005 | Simultaneity Fault: Safe torque off lines don't match each other | Simultaneity Fault: Safe torque off lines don't match each other | Contact Customer Support |
| F9006 | SMM in failed state | SMM detected a safety I/O failure and faulted. This can be caused by a number of things: digital I/O pulse failed, STO pulse failed, encoder position failure, or serial communication failed. | Determine cause and replace necessary hardware if issue reoccurs |
| F9007 | Safe brake parameters inconsistent | The safe parameters, AXIS#.SAFE.SBC.BRAKE#ATTACHED, indicate a brake is attached, but non-safe brake keywords, AXIS#.MOTOR.BRAKE, AXIS#.BRAKE, do not and drive was enabled. |
From the safety parameter screen in WorkBench under safe brake control (SBC), verify that the SBC Brake parameters agree with the drive related parameters that a brake is either configured or not.
The keywords AXIS#.MOTOR.BRAKE, AXIS#.BRAKE, and safe brake control configuration (SBC) all must agree with each other. For example, if no brake is present AXIS#.MOTOR.BRAKE should be 0 and safe parameters for SBC should indicate ‘Not Configured’. If brake is present, AXIS#.MOTOR.BRAKE should be 1, BRAKE#.AXIS should be assigned to proper axis, and safe parameters for SBC should be set to ‘Configured…’
AXIS#.SAFE.SBC.BRAKE1ATTACHED and AXIS#.SAFE.SBC.BRAKE2ATTACHED can be verified for the currently active safe parameters. |
| W1000 | Fan stalled. | Fan speed is too slow | Power Cycle drive, if problem persists Contact Customer Support |
| W1001 | Sync timer PLL. | FPGA Synchronization is off | Update to latest firmware, if problem persists contact Customer Support |
| W2001 | Drive foldback imminent! Reduce Load. | Current command is high enough to trip Drive Foldback threshold soon. | Decrease current command by softening tuning gains or a less aggressive motion trajectory. If problem persists, application may require a drive with larger power rating. |
| W2002 | Motor foldback imminent! Reduce Load. | Current command is high enough to trip Motor Foldback threshold soon. | Decrease current command by softening tuning gains or a less aggressive motion trajectory. If problem persists, application may require a motor with larger power rating. |
| W2003 | Motor I2t load! Reduce load. | Current command is high enough to trip Motor I²t threshold soon. | Decrease current command by softening tuning gains or a less aggressive motion trajectory. If problem persists, application may require a motor with larger power rating. |
| W2006 | Bus over voltage. | Line voltage spiked above VBUS.OVWTHRESH, or motor back emf generated voltage above VBUS.OVWTHRESH. | Clear Faults, if problem persists determine source of voltage spike. If problem is power related; power conditioning may be required. If voltage spike is due to motor back-emf, a regen resistor may be required for the application |
| W2007 | Bus under voltage. | Bus voltage dipped below VBUS.UVWTHRESH | Check supply voltage |
| W2008 | Bus capacitor overloaded. | Internal voltage spiked above VBUS.OVWTHRESH, or motor back emf generated voltage above VBUS.OVWTHRESH. | Clear Faults, if problem persists determine source of voltage spike. If problem is power related; power conditioning may be required. If voltage spike is due to motor back-emf, a regen resistor may be required for the application |
| W2010 | Regen energy critical. | Regen resistor is reaching its capacity | Decrease aggressiveness of motion profile, or use larger size regen resistor |
| W2011 | No Power on IO 24V Rail | 24 volts was not detected on x21 connector. Note: digital outputs will not be functional without 24V. | Connect +24V to B3 (24V_I/O) on x21 and GND to B4 (GND_I/O) on x21 and verify wire integrity |
| W2012 | Inconsistent mains voltage | AC mains voltage is consistent with VBUS.ACNOMINAL. | Adjust VBUS.ACINOMINAL or ac main voltage. |
| W2500 | Control Over Temp Sensor 1. | Internal control board temperature is overheating | Increase air circulation around drive box, check fan operation. If problem persists contact Customer Support |
| W2501 | Power Over Temp Sensor 1. | Internal power board temperature is overheating | Increase air circulation around drive box, check fan operation. If problem persists contact Customer Support |
| W2502 | Control Under Temp Sensor 1. | Internal control board is getting below specified operating temperature | Check environment the drive is operating in. |
| W2503 | Power Under Temp Sensor 1. | Internal power board is getting below specified operating temperature | Check environment the drive is operating in. |
| W3100 | An axis has a duplicate Actual Position Feedback block. | Across all of the active MechaWare models, there is more than one Actual Position Feedback block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3101 | An axis has a duplicate PL.CMD block. | Across all of the active MechaWare models, there is more than one PL.CMD block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3102 | An axis has a duplicate PL.ERR block. | Across all of the active MechaWare models, there is more than one PL.ERR block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3103 | An axis has a duplicate Position Int Out block. | Across all of the active MechaWare models, there is more than one Position Int Out block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3104 | An axis has a duplicate VL.CMD block. | Across all of the active MechaWare models, there is more than one VL.CMD block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3105 | An axis has a duplicate VL.FB block. | Across all of the active MechaWare models, there is more than one VL.FB block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3106 | An axis has a duplicate VL.ERR block. | Across all of the active MechaWare models, there is more than one VL.ERR block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3107 | An axis has a duplicate Trajectory VCmd block. | Across all of the active MechaWare models, there is more than one Trajectory VCmd block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3108 | An axis has a duplicate IL.FF block. | Across all of the active MechaWare models, there is more than one IL.FF block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3109 | An axis has a duplicate OpenLoopFeedback block. | Across all of the active MechaWare models, there is more than one OpenLoopFeedback block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3110 | An axis has a duplicate VelocityPIOut block. | Across all of the active MechaWare models, there is more than one VelocityPIOut block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3111 | An axis has a duplicate PreBodeExcite block. | Across all of the active MechaWare models, there is more than one PreBodeExcite block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3112 | An axis has a duplicate Motor Torque block. | Across all of the active MechaWare models, there is more than one Motor Torque block for an axis. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3113 | A duplicate AnalogOut block exists. | Across all of the active MechaWare models, there is more than one Analog Out block with the same output number. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3114 | A duplicate DigitalOut block exists. | Across all of the active MechaWare models, there is more than one Digital Out block with the same output number. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3115 | A duplicate UserBuffer block exists. | Across all of the active MechaWare models, there is more than one UserBuffer block with the same output number. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3116 | A duplicate Simulated Feedback block exists. | Across all of the active MechaWare models, there is more than one Simulated Feedback block with the same output number. |
1) Verify correct models are active 2) Modify user models and remove extra blocks |
| W3117 | An axis is missing its PL.CMD block. | Across all of the active MechaWare models, an axis is missing it's PL.CMD block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3118 | An axis is missing its PL.ERR block. | Across all of the active MechaWare models, an axis is missing it's PL.ERR block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3119 | An axis is missing its Position Int Out block. | Across all of the active MechaWare models, an axis is missing it's Position Int Out block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3120 | An axis is missing its VL.CMD block. | Across all of the active MechaWare models, an axis is missing it's VL.CMD block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3121 | An axis is missing its VL.FB block. | Across all of the active MechaWare models, an axis is missing it's VL.FB block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3122 | An axis is missing its VL.ERR block. | Across all of the active MechaWare models, an axis is missing it's VL.ERR block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3123 | An axis is missing its Trajectory VCmd block. | Across all of the active MechaWare models, an axis is missing it's Trajectory VCmd block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3124 | An axis is missing its IL.FF block. | Across all of the active MechaWare models, an axis is missing it's IL.FF block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3125 | An axis is missing its OpenLoopFeedback block. | Across all of the active MechaWare models, an axis is missing it's OpenLoopFeedback block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3126 | An axis is missing its VelocityPIOut block. | Across all of the active MechaWare models, An axis is missing it's VelocityPIOut block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3127 | An axis is missing its PreBodeExcite block. | Across all of the active MechaWare models, an axis is missing it's PreBodeExcite block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3128 | An axis is missing its Motor Torque block. | Across all of the active MechaWare models, an axis is missing it's Motor Torque block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3129 | An axis is missing its Position Command block. | Across all of the active MechaWare models, an axis is missing it's Position Command block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3130 | An axis is missing its Position Feedback block. | Across all of the active MechaWare models, an axis is missing it's Position Feedback block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3131 | An axis is missing its Velocity Command block. | Across all of the active MechaWare models, an axis is missing it's Velocity Command block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3132 | An axis is missing its Bode Torque block. | Across all of the active MechaWare models, an axis is missing it's Bode Torque block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W3133 | An axis is missing its Bode Velocity block. | Across all of the active MechaWare models, an axis is missing it's Bode Velocity block. |
1) Verify correct models are active 2) Modify user models and add required block for each axis |
| W4000 | Feedback Parity Warning | Feedback Parity Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4001 | Feedback Overrun Warning | Feedback Overrun Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4002 | Feedback Framing Warning | Feedback Framing Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4003 | Feedback CRC Warning | Feedback CRC Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4004 | Feedback Communication Timeout Warning | Feedback Communication Timeout Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4005 | Feedback Initialization Sequence Warning | Feedback Initialization Sequence Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4006 | Feedback Temperature Warning | Feedback Temperature Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4007 | Feedback battery Warning | Feedback battery Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4008 | Feedback Sensor Warning | Feedback Sensor Warning | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4009 | Feedback Device-Unique Warning 0 | Feedback Device-Unique Warning 0 | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4010 | Feedback Device-Unique Warning 1 | Feedback Device-Unique Warning 1 | Check Feedback Settings, if problem persists, Contact Customer Support |
| W4011 | Warning: Gearing feedback source fault. | Fault condition was detected on position feedback device referenced by AXIS#.GEAR.FBSOURCE. | . |
| W5000 | Motor overheated. | Motor overheated. | Check ambient temperature. Check motor mounting heat sink capability |
| W5001 | Brake override active | Brake override active | The parameter AXIS#.MOTOR.BRAKECONTROL overrides actual brake control of the drive. |
| W5007 | Brake override active, but no brake configured. | Brake override is active on an axis that has no brake configured. | The parameter AXIS#.MOTOR.BRAKECONTROL overrides actual brake control of the drive. |
| W5500 | Wake and Shake - Over speed | AXIS#.WS.VTHRESH was exceeded. | Increase AXIS#.WS.VTHRESH value or reduce AXIS#.WS.IMAX or AXIS#.WS.T . |
| W6000 | Velocity limit violation, exceeding max limit. | A new target velocity calculated internally due to an exception, and is being limited due to user velocity limit. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. Check motion task target velocity settings and parameters to make sure that the values entered will not exceed the AXIS#.VL.LIMITP and AXIS#.VL.LIMITN setting. |
| W6001 | Following error magnitude fault. | Motor did not follow command values. Motor exceeded maximum allowed position following error AXIS#.PL.ERRWTHRESH . | Check feedback commutation setup and tuning parameters. |
| W6002 | Fault on FB2 is preventing remote commutation for FB1. | Attempt to issue motion task before the axis is homed. Axis must be homed before motion task can start. | Change opmode or home axis. |
| W6003 | OPMODE incompatible with CMDSOURCE | This warning is generated when the drive is enabled and the gearing command source is selected at the same time as torque or velocity op-mode. | Select a different AXIS#.OPMODE and AXIS#.CMDSOURCE combination. |
| W6004 | Zero velocity when using induction sensorless feedback type in torque mode. | Zero velocity when using induction sensorless feedback type in torque mode. | Check motor wiring and tuning parameters. If problem persists contact Customer Support |
| W6005 | Velocity has been limited commutation speed to less than 600Hz to meet ECCN 3A225 requirements. | Motor Velocity has exceeded the allowed commutation speed (599Hz). | Refer to ECCN 3A225 Limitations for Induction Motors. |
| W6006 | Positive limit switch triggered. | Either a digital input is configured as positive limit switch (DINx.MODE 18) and its state is “off” OR a positive software position limit is configured (AXIS#.SWLS.EN) and the actual position AXIS#.PL.FB is greater than the configured limit (see also AXIS#.SWLS.LIMIT# / ). | Move the load away from the limits. |
| W6007 | Negative limit switch triggered. | Either a digital input is configured as negative limit switch (DINx.MODE 19) and its state is “off” OR a negative software position limit is configured (AXIS#.SWLS.EN) and the actual position AXIS#.PL.FB is less than the configured limit (see also AXIS#.SWLS.LIMIT# / ). | Move the load away from the limits. |
| W6008 | Using derivative of position when using sensorless feedback type in position mode | Using derivative of position when using sensorless feedback type in position mode | Sensorless operation is not allowed for POSITION MODE - change AXIS#.OPMODE to Velocity Mode |
| W6009 | Following motion failed; check motion parameters. | Activation of the following motion task failed due to incompatible parameters, or motion task does not exist. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. Check following motion task settings and parameters to make sure that the values entered will produce a valid motion task. |
| W6010 | Target position crossed due to stop command. | The motion task crosses the target position after triggering a AXIS#.STOP command. This situation can happen when processing a change-on-the-fly motion task and triggering a AXIS#.STOP command close to the target position of the currently running motion task. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6011 | HomingThe Homing procedure allows, based on a position measurement, to set a position offset to the motor in order to ensure it is physically at the home position index pulse not found. |
A homing mode with index detection is activated, and index pulse is not detected while moving across the range determined by the hardware limit switches. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6012 | Homing reference switch not found. | A homing mode with reference switch detection is activated and the reference switch is not detected while moving across the range determined by the hardware limit switches. | Activation of any new motion or using ofAXIS#.CLRFAULTS will clear the warning. |
| W6014 | Motion task activation failed. | Activation of the motion task failed due to incompatible parameters, or motion task does not exist. This warning can appear upon an AXIS#.MT.MOVE command. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. Check motion task settings and parameters to make sure that the values entered will produce a valid motion task. |
| W6015 | Homing procedure failed. | Homing error observed during the operation of homing procedure. | Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6017 | Motion task target position is out. | This warning appears with W6014. This warning is triggered when you try to trigger a motion task with an absolute target position outside of the selected modulo range (see also AXIS#.MT.CNTL). | Move the absolute target position of the motion task within the modulo range. Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6018 | Motion task target position is out of software-limits. | Motion Task position has passed a software limit switch | Review software limit switch configuration and motion task configurations and remove incompatibilities. |
| W6019 | Invalid bit combination in the motion task control word. | This warning appears with W6014. This warning is triggered when you try to trigger a motion task with an invalid bit combination in the motion task control word (see also AXIS#.MT.CNTL). | Correct the AXIS#.MT.CNTL setting for the specific motion task. Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6020 | 1:1 profile cannot be triggered on the fly. | This warning appears with W6014. This warning is triggered when you try to trigger a 1:1 profile table motion task while another motion task is currently running. | 1:1 profile table motion tasks should be started from velocity 0. Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6021 | Customer profile table is not initialized. | This warning appears with W6014. This warning is triggered when you try to trigger a motion task that uses a customer profile table for generating the velocity profile and when the selected profile table is empty (see AXIS#.MT.CNTL and MT.TNUM. | Change the MT.TNUM parameter for this specific motion task in order to use an initialized profile table. Activation of any new motion or using of AXIS#.CLRFAULTS will clear the warning. |
| W6022 | Motion task activation is currently pending. | A motion task tried to execute before the previous task was able to execute | Review application timing and allow for adequate time for each motion task to activate before requesting a subsequent motion. |
| W6023 | Homing maximum distance exceeded. | Homing maximum distance exceeded. | Review tuning and parameter AXIS#.HOME.MAXDIST |
| W6024 | Motion task is not initialized. | This warning appears with W6014. This warning is triggered when you try to trigger a non-initialized motion task. | Initialize the motion task first before starting the task. Activation of any new motion or using of DRV.CLRFAULTS will clear the warning. |
| W6025 | Homing and feedback mismatch. | A homing mode is selected which can not work with the current feedback. For example homing modes 3, 6, 10 and 11 all require the feedback to provies a Z / index pulse and not all feedbacks provide this signal.If the homing move is started then it may run continuously because it is missing a signal from the feedback. | You will either need to select a different homing mode or change the feedback being used. |
| W6026 | Current homing mode requires AXIS#.HOME.IPEAK to be set by user | The homing mode selected requires that AXIS#.HOME.IPEAK be set to non-zero. | Set AXIS#.HOME.IPEAK to a value non-zero. |
| W6027 | Current command saturated | AXIS#.IL.CMD has exceeded AXIS#.IL.LIMITP or AXIS#.IL.LIMITN . | Increase current limits (AXIS#.IL.LIMITP or AXIS#.IL.LIMITN) or reduce load by decreasing trajectory acceleration/velocity. |
| W6028 | Gear feedback source is invalid | The feedback selected as the gearing source is either uninitialized or assigned to the same feedback being used as the commutation, velocity, or position feedback source. | Verify AXIS#.GEAR.FBSOURCE is not 0 and does not match the feedback being used for AXIS#.IL/VL/PL.FBSOURCE. |
| W7000 | Fieldbus Communication lost. | All fieldbus communication was lost. | Check fieldbus connections (X11/X12), settings, and control unit. |
| W7001 | Fieldbus Sync frames lost. | The fieldbus lost synchronization. | Check fieldbus connection or the settings of your fieldbus master. |
| W9000 | Warning: Safe torque off. | Safe torque off function has been triggered. | Reapply supply voltage to STO if safe to do so. |
| W9001 | Warning: Brake Test Time Overflow | A safe brake test has not been executed within the configured time limit | Extend safe brake test time limit or execute a safe brake test |
| W9002 | Warning: SMM Over Temperature | Safe motion module is over temperature | Replace hardware |
| W9003 | Warning: SMM State not operational | Safe motion module is not ready to enable. | Verify safe id and safe parameters are validated and correct.Check for other faults on the safe motion monitor. |
| W9004 | SMM I/O failure detected | SMM I/O failure detected | Update to latest firmware, if problems persist, contact Customer Support |
| W9007 | Safe brake parameters inconsistent | The safe parameters, AXIS#.SAFE.SBC.BRAKE#ATTACHED, indicate a brake is attached, but non-safe brake keywords, AXIS#.MOTOR.BRAKE, AXIS#.BRAKE, do not and drive was enabled. |
From the safety parameter screen in WorkBench under safe brake control (SBC), verify that the SBC Brake parameters agree with the drive related parameters that a brake is either configured or not.
The keywords AXIS#.MOTOR.BRAKE, AXIS#.BRAKE, and safe brake control configuration (SBC) all must agree with each other. For example, if no brake is present AXIS#.MOTOR.BRAKE should be 0 and safe parameters for SBC should indicate ‘Not Configured’. If brake is present, AXIS#.MOTOR.BRAKE should be 1, BRAKE#.AXIS should be assigned to proper axis, and safe parameters for SBC should be set to ‘Configured…’
AXIS#.SAFE.SBC.BRAKE1ATTACHED and AXIS#.SAFE.SBC.BRAKE2ATTACHED can be verified for the currently active safe parameters. |
|
Stay Connected with Kollmorgen       
|
Copyright © 2018 Kollmorgen |
|